Migration skills state explicit template and upgrade conditions - #581

Exact delivery and source evidence

The scope is limited to the linguistic handback in #561. Both complete skills are reviewed. Before editing, exact source spans, expected replacements, and protected-content checks were recorded in the issue and in session-local JSON evidence. All three target statements were absent before editing and match their recorded replacements at the final head.

Scoped comparison: base main at 64ffb1d87f86bd5d487891fdb140b78385a00531; final pushed head 21cc8b3c5f6f5bce6fe245ffd181fea5d0c496c4 on migration-framing-prose. The branch contains two small commits: c43c36e1012859388d378a838c27e318893d933c for the two v8 framing spans, then 21cc8b3c5f6f5bce6fe245ffd181fea5d0c496c4 for the two-line Zensical framing. This draft opened immediately after the first commit. Live issue ownership and unchanged main source blobs were rechecked before each commit.

Only these two files change, with 11 insertions and 8 deletions:

Protected content

A one-off comparison reverses only the three recorded framing replacements and compares every other source text byte exactly, with CRLF normalized to LF. All ordered front matter, headings, fenced blocks, inline literals, and links also compare exactly.

This protects the exact caller YAML, triggers, permissions, concurrency, v8 reference, secrets, TestData examples, template/version selection, anatomy tree, layout alternatives, optional source directories and test phases, optional assets, migration actions, validation procedures, stop conditions, and normative force. No example becomes universal. All other skills, proposal branches, metadata, site design, runtime, repository tests, and dependencies remain unchanged. No migration command runs.

Existing checks and limits

The repository Markdown configuration passes on both files with zero issues (markdownlint-cli2 0.24.0, markdownlint 0.42.0). The repository spelling configuration and git diff --check pass. The existing YAML parser accepts both unchanged front-matter maps; both unchanged plugin metadata JSON files parse. The one relative skill target resolves. All 20 links remain exact. No standalone plugin link/front-matter checker exists in this checkout; unchanged external URLs are not claimed as network-checked.

The plain textlint CLI reports no rules before edits and cannot resolve its configured rule packages on this host. After the actual missing-package failure, those tools were restored only in the npm cache. The existing textlint 15.8.0, terminology 5.2.16, and comments 1.3.0 rules pass through their installed API with the unchanged repository options and Markdown plugin: zero messages on both immutable source files and both final files. An anonymous incorrect-term probe confirms rule execution, and a comment probe confirms the existing filter. No repository tooling or dependency is added.

All hosted checks pass for this exact head: CodeQL, Analyze (actions), and Lint code base. Copilot review 5769461963 approves 21cc8b3c5f6f5bce6fe245ffd181fea5d0c496c4 with no inline comments. No hosted result is assumed from local checks.

Standards and completion boundary

The fixed MSX writing source supplies the Documentation Model, Natural Language, Writing Guide, Markdown, Documentation, guide template, and Task/PR formats. The official STE overview and FAQ, relevant Issue 9 rules and dictionary entries, and en-US inform only the released wording. The Issue 9 manual stays local; its PDF checksum matches the official record. No certified or full STE conformance is claimed.

The README, plugin structure, shared guides, headings, anchors, and metadata need no change for this bounded framing correction. Implementation, local checks, and hosted checks are complete. Independent current-head content review accepts 21cc8b3c5f6f5bce6fe245ffd181fea5d0c496c4: both skill diffs stay within the exact framing handback, and the selected-revision/requested-upgrade conditions preserve templates, paths, optional/required distinctions, scope, and procedure. No further source change is requested. The PR stays draft and the issue stays open until a separately authorized merge. No merge, ready transition, auto-merge, Agent merge, release-label, or lifecycle setting changes.

Issue-convergence scope: the exact handback and open migration-title issues. No additional issue is fully resolved by this two-file diff. Only #561 has a closing reference.

• Resolves [documentation-writing-alignment] State migration skill conditions without session-specific wording #561
• References 🚀 [Feature]: Module repositories share one auditable baseline #525, 📖 [Docs]: Configure retained releases and current PR feedback #535, and Release authors can write self-contained upgrade notes #537 for unchanged template/caller/authoring ownership.